The mediocre user's guide to JACOsub scripting.
Version 0.4
Last revised:  08/99
Contact:  momopi@mail.com
 
Note:  This document is formatted for Windows Wordpad, and should display fine with Notepad.exe.  Remember to enable word wrap option.  The mediocre user's guide is made possible by comments and suggestions from numerous JACOsub users and the software author himself.



The Mediocre user's guide to JACOsub scripting.

I.     Introduction.
II.    General Rules to follow.
III.   Script Headers.
IV.    Margin, color, and fonts.
V.     Directives.
VI.    Combined headers & directives.
VII.   Examples.
VIII.  Palette switching.
VIV.   WinUAE.
X.     Amiga upgrades.


I.  Introduction:

Computer users are often divided into two groups: the high priests in white lab coats who can write an operating system with DEBUG.EXE, and the coworker who'd use the CDROM drive as a cup holder & the mouse as a foot pedal.

This document is written for the non-expert, and non-idiot JACOsub users:  the mediocre guy who'd ask "how should I format my scripts" and "what RGB value do I use for Blue?".  This document will teach you how to properly format your scripts, insert headers, and add margin, color, font, & directive settings.

If you can recite all the commands in JACOsub.doc from memory, this document is not for you.  You really need to get out more -- the Sun is your friend.


Before we get started, here's some common questions and answers:

Q.  What is that lower case "n" in #Dn, CFn, or \Cn  I see in the documentation?
A.  The lower case "n" is often used as a numeric variable.  #Dn means #D plus a number, like #D1, #D2.  Note:  this does not apply to the  \n  command.

Q.  I see the letter "D" and "E" in the color settings.  Why is it not 0-15?
A.  Some JACOsub scripts use hexadecimal (0-9 plus letters) instead of decimal (numbers) for color settings.  When converting Hexadecimal to Decimal, the numbers 0-9 stay the same.  Starting from the number 10, Hexadecimal use letters.  10=A, 11=B, and so on.  Here's a chart:

Decimal   Hexadecimal
  0-9       0-9
  10        A
  11        B
  12        C
  13        D
  14        E
  15        F


II.  General rules to follow:

a.  Neatness.  Make your script neat and easy to read.

Instead of:
0:07:37.42 0:07:38.42 {Asuka Jr.} Whaddaya mean?!
0:07:38.42 0:07:39.26 {Meimi} What?!
0:07:40.95 0:07:42.29 {Meimi} Don't stop me, Seira.
0:07:42.29 0:07:43.94 {Nun} I'm not Seira.
0:07:46.96 0:07:47.73 {Meimi} Seira...
0:07:48.80 0:07:52.52 {Nun} Haneoka-san, Asuka-san. Go stand in the hallway!
0:07:52.77 0:07:53.76 {Meimi & Asuka Jr.} Yes...

Make it look neat:
0:07:37.42 0:07:38.42 {Asuka} Whaddaya mean?!
0:07:38.42 0:07:39.26 {Meimi} What?!
0:07:40.95 0:07:42.29 {Meimi} Don't stop me, Seira.
0:07:42.29 0:07:43.94 {Nun  } I'm not Seira.
0:07:46.96 0:07:47.73 {Meimi} Seira...
0:07:48.80 0:07:52.52 {Nun  } Haneoka-san, Asuka-san. Go stand in the hallway!
0:07:52.77 0:07:53.76 {Meimi/Asuka} Yes...

It's okay if some lines don't fit in the 5 spaces between { }, or however many spaces you prefer.  Don't over-format, or else you'd end up with a monstrosity like this:
0:07:37.42 0:07:38.42 {,,,,Asuka Jr.,,,} Whaddaya mean?!
0:07:38.42 0:07:39.26 {,,,,,Meimi,,,,,,} What?!

b.  Consistency.  Make your script consistent.

Be consistent with your color usage.  If you're using White for silent speech (thoughts) and Green for alternate speech, don't change your mind 5 lines down and throw in Pink.  Yes it's cute, and annoying.

For font/color settings, use directives (#Dn) instead of putting the font codes in the timed script area.

Instead of:
0:07:38.42 0:07:39.26 F1CF5 {Meimi} What?!
0:07:40.95 0:07:42.29 F1CF1 {Meimi} Don't stop me, Seira.

Set #Dn to declare F1CFn and use:
#
#D1 F1CF5     # Directives should be placed before the timed script area.
#D2 F1CF1     # Explain what the directive does here, e.g. "JACOsub 29 font, Green color."
#
0:07:38.42 0:07:39.26 D1 {Meimi} What?!
0:07:40.95 0:07:42.29 D2 {Meimi} Don't stop me, Seira.

c.  Simplicity.  It's easier to port your scripts to other people's machines if you use "general" commands, such as VT, VM, VB, JR, JL, and \n, instead of specific font positioning with VPn.

Instead of:
0:07:38.42 0:07:39.26 D1VP80 {Meimi} What?!

Use:
0:07:38.42 0:07:39.26 D1VT {Meimi} \nWhat?!

One of the greatest assets to JACOsub is the ability to position subtitles anywhere on the screen via mouse positioning.  While this is a very useful for complex on-screen displays, you should minimize its use.  Usually, top, middle, bottom, right, and left positioning is sufficient.  The "reader" will appreciate your consistency in font placement.


III.  Script headers:

a.  Remember to plug in a banner for Alex on top:

# JACOsub script file
# For information about JACOsub, contact Alex Matulich
# (703) 413-0215  Internet: matulich_a@seaa.navsea.navy.mil
#                 WWW:      unicorn.us.com/jacosub
#

b.  Proper credits:  (episode number, episode title)

# Goldfish Warning Episode 160:  We're going shopping!
# Version 0.1
# Translation by:  Miro Pihkanen
# Script timing by:  Fred Leggett
# Editing by:  Alan L. Batongbacal
#

Make sure you state the title of the show, episode number(s), and script revision number.

Note from Fred:  If the script contains more than one installment of a series, I would include the above again just before the start of the next episode.  If any credit data is the same for the entire timing file, then it can be included as a global notation at the beginning. However, specific episode information (number & title) should be properly documented right before the beginning of that episode's section.

c.  Insert a note on sync point, and proper font positioning:

#  /* Readme.NOW */
#
# Sync Point:  Beginning of LD, after script pause at #C 0.00.02.01
# Positioning:  Op song lyrics should be just above the Japanese text.
#

d.  Shift/Ramp values

If you don't know these by now, you really need to read \JACOsub\documentation\#?.doc.

#T100                 #  Time units per second.
#S0.00                #  Shift value in seconds.
#R0.00                #  Ramp value in seconds.


IV.  Margin, color, and fonts:

a.  Set left-right margins, so people with less than 3.6 meter projection screen can see what's on the edges:

#DHL4HR96             # If this isn't enough, try #DHL6HR94 or greater.

This will set Left-margin to 4% of screen, and Right margin to 96% of screen.  Remember that this is your Amiga's setting, not your TV's.

b.  Set RGB (Red-Green-Blue) color values, so others won't have to guess what you're using:

#P0  9 10 11          # color 0 - (Background) Red, Green, Blue (Max value 15)
#P1  1 13  8          # color 1 - font alternate face color (Green)
#P2  0  0  0          # color 2 - this MUST be your fonts' shadow/outline color (Black)
#P3 13 13  0          # color 3 - font primary face color (Yellowish)
#P4  6 12 13          # color 4 - font primary face color (Blue)
#P5  0 13 13          # color 5 - font primary face color (Cyan)
#P6 13  8 13          # color 6 - font primary face color (Pink)
#P7 13 13 13          # color 7 - font primary face color (White)

The above values are what I use with SuperGen SX, and 8 color Workbench.  Avoid using RGB values of 14 or greater, and don't use 16 color mode -- it'd run slow on non-accelerated Amigas.  See JACOsub.doc for more RGB color settings.

If you're running an Amiga 3000 in super high-res mode, you're limited to 4-color palette.  Older Amigas may have this limitation as well.  JACOsub supports up to 10 color palettes, the CPn command is used to switch between palettes.  See section VII for examples.

Note from Alex:  A1200/4000 models may allow more colors in superhighres mode.  Even if they do, the additional bitplanes may cause frame generation to slow down a bit.  You should always set the minimum colors you can get away with.  For many scripts, the default 4 color display (giving 2 usable title colors) is sufficient, and eight is usually more than enough for most.

Here's what Simon (Nautilus/UK) use for his JACOsub color config:
#P0  9 a b                   #    9 10 11
#P1  1 d 8                   #    1 13  8     Green
#P2  0 0 0                   #    0  0  0
#P3  d d 5                   #   13 13  5     Yellow, for standard subbing
#P5  f f 0                   #   15 15  0     Bright Yellow for signs
#P7  0 b e                   #    0 11 14     Bright Blue
#P15 d d d                   #   13 13 13     White

c.  Set fonts, so people won't have to guess what font you're using:

#F1 Jacosub.font 29          # Default subtitle font for this script.
#F2 FuturaB.font 20          # Small font for credits.
#F3 Helvetish3.font 21       # Alternate font.
#F4 Jacosub.font 32          # Larger font for titles.  Avoid using fat outline/shadow.


V.  Directives:

Don't use global font directives like these:
#DF1
#DFSSE3
#DF01

It might look okay with your default font, but, your alternate fonts will look like a blob (they'd assume your global #FOn and #FSSEn settings).  Use #Dn and assign a directive to every line in your timed script.  This will also make global modifications easier.

Here are some typical directives I use.  JACOsub supports up to 30 directives:

#D1  VH120F1FO2FSSE1             # Yellow default Text on bottom, for JACO 29.
#D2  VH120VTF1CF1FO2FSSE1        # Green on top.  Try these with FO1FSSE2, FSSE2, FO2:2/FO2:3 w/FSSE0
#D3  VH120F1CF1FO2FSSE1          # Green on bottom.
#D4  VH120VTF1CF7FO2FSSE1        # White on top
#D5  VH120F1CF7FO2FSSE1          # White on bottom
#D6  VH120F1CF4FO2FSSE2          # Blue on bottom, song, FSSE2 think border to cover Japanese lines.
#D7  VH120VTF2CF7FO2FSSE2        # White on top, Small (FuturaB 20) font.
#D8  VH120F2CF1FO2FSSE2          # Green on bottom, Small (FuturaB 20) font.
#D9  VH120VTF2CF4FO2FSSE2HL10JL  # Blue on Left, 10% margin, for Credits, FuturaB.
#D10 VH120VTF2CF6FO2FSSE2HL50JL  # Pink on Right, 50% margin, for Credits, FuturaB.
#D11 VH120F1FO2FSSE1VMJLJBC      # Yellow, Intro Credits, JLJBC:  Left Justify, Justify Block Center.
#D12 F4CF7VM                     # White, Large font (JACO 32) for credits.
#D13 VTVH130F3CF1FO4FSSE1        # Green on top, alternate Text (Helvetish3), try w/FSSE2.
#D14 VH130F3CF4FO4FSSE1          # Blue on bottom, alternate Text (Helvetish3), try w/FSSE2.

Note from Alex:  It might make the script easier to understand if you associated name tags to those directives.

Directive notes:

VH120:  If you're using JACOsub 29 point with "fat" font settings (FO2, FSSE1), you need to use VH120 to increase line height and avoid screen refresh problems.  Otherwise, you'll get bits from a previous line left over on your screen.  The "120" means 120% of normal spacing between lines (20% increase).  So, VH200 would mean double-spacing.

Note from Alex:  This is only true for fonts that need to be fattened, not fonts that already have fat outlines and shadows as part of their character bitmaps.  It's a good idea to adjust the line height by a percentage greater or equal to the height increase caused by fattening.  So, FO2 FSSE1 will cause 5 additional pixels of height (2 above and eblow for the outline, and 1 for the shadow).  This is a 17.2% increase.  So VH118 (line height 118% of normal) should suffice.

FO2FSSE1:  Try using FO1FSSE2, FSSE2, FO2:2FSSE0, or FO2:3FSSE0.  Remember the "O" in FO1 is the letter O, not the number zero (0) in FSSE0.

HL10JL & HL50JL:  This will position your text at 10% from left, and 50% from left, with left-justification.  This is pretty nice for credits, remember to use a smaller font (futuraB 20).

If you don't want to mess with all these complicated Font Outline (FOn) and Drop-Shadow (FSdn) commands just use the JACOsub.font 32 "as is".  It looks pretty good by default.

When you use directives, instead of:
0:07:37.42 0:07:38.42 F1CF1FO2FSSE1 {Asuka} Whaddaya mean?!
0:07:38.42 0:07:39.26 F1FO2FSSE1    {Meimi} What?!
0:07:40.95 0:07:42.29 F1FO2FSSE1    {Meimi} Don't stop me, Seira.
0:07:42.29 0:07:43.94 F1CF7FO2FSSE1 {Nun  } I'm not Seira.

You use this instead:
0:07:37.42 0:07:38.42 D3 {Asuka} Whaddaya mean?!
0:07:38.42 0:07:39.26 D1 {Meimi} What?!
0:07:40.95 0:07:42.29 D1 {Meimi} Don't stop me, Seira.
0:07:42.29 0:07:43.94 D5 {Nun  } I'm not Seira.

Remember that you can still add JACOsub commands to a directive.  Say you want to use #D12 (F4CF7VM) on the bottom, you can add  VB  to the directive like this:
0:07:42.29 0:07:43.94 D12VB {Nun  } I'm not Seira.


VI.  Combined headers & directives:

Here's what the top section of a timed script would look like, if you used the examples from above:

# JACOsub script file
# For information about JACOsub, contact Alex Matulich
# (703) 413-0215  Internet: matulich_a@seaa.navsea.navy.mil
#                 WWW:      unicorn.us.com/jacosub
#
# Goldfish Warning Episode 161:  We're going shopping!
# Version 1.0
# Translation by: Miro Pihkanen
# Script timing by:  Fred Leggett
# Editing by:  Alan L. Batongbacal
#
#  /* Readme.NOW */
# Sync Point:  Beginning of LD, after script pause at #C 0.00.02.01
# Positioning:  Op song lyrics should be just above the Japanese text.
#
#T100
#S0.00
#R0.00
#
#DHL4HR96             # If this isn't enough, try #DHL6HR94 or greater.
#
#P0  9 10 11          # color 0 - (Background) Red, Green, Blue (Max value 15)
#P1  1 14  8          # color 1 - font alternate face color (Green)
#P2  0  0  0          # color 2 - this MUST be your fonts' shadow/outline color (Black)
#P3 14 14  0          # color 3 - font primary face color (Yellowish)
#P4  6 12 14          # color 4 - font primary face color (Blue)
#P5  0 14 14          # color 5 - font primary face color (Cyan)
#P6 14  8 14          # color 6 - font primary face color (Pink)
#P7 14 14 14          # color 7 - font primary face color (White)
#
#F1 Jacosub.font 29              # Standard subtitle font.
#F2 FuturaB.font 20              # Small font.
#F3 Helvetish3.font 21           # Alternate font.
#F4 Jacosub.font 32              # Larger font for titles and stuff.
#
#D1  VH120F1FO2FSSE1             # Yellow default Text on bottom, for JACO 29.
#D2  VH120VTF1CF1FO2FSSE1        # Green on top.  Try with FO1FSSE2, FSSE2, FO2:2/FO2:3 w/FSSE0
#D3  VH120F1CF1FO2FSSE1          # Green on bottom.
#D4  VH120VTF1CF7FO2FSSE1        # White on top
#D5  VH120F1CF7FO2FSSE1          # White on bottom
#D6  VH120F1CF4FO2FSSE2          # Blue on bottom, Song, FSSE2 thick border to cover Japanese text.
#D7  VH120VTF2CF7FO2FSSE2        # White on top, Small (FuturaB 20) font.
#D8  VH120F2CF1FO2FSSE2          # Green on bottom, Small (FuturaB 20) font.
#D9  VH120VTF2CF4FO2FSSE2HL10JL  # Blue on Left, 10% margin, for Credits, FuturaB.
#D10 VH120VTF2CF6FO2FSSE2HL50JL  # Pink on Right, 50% margin, for Credits, FuturaB.
#D11 VH120F1FO2FSSE1VMJLJBC      # Yellow, Intro Credits, JLJBC: Left Justify, Justify Block Center.
#D12 F4CF7VM                     # White, Large font (JACO 32) for credits.
#D13 VTVH130F3CF1FO4FSSE1        # Green on top, alternate Text (Helvetish3), try w/FSSE2.
#D14 VH130F3CF4FO4FSSE1          # Blue on bottom, alternate Text (Helvetish3), try w/FSSE2.

And that's it!  Feel free to cut & past this into your script, and modify them as you see fit.


VII.  Examples:

Here are some examples for mediocre JACOsub user.  Assume we're using D1, and we need to position the line in various places:

a.  People speaking from Right / Left, on screen at the same time:

0:07:37.42 0:07:38.42 D1JR {Asuka} Whaddaya mean?!
0:07:38.42 0:07:39.42 D1JL {Meimi} What?!

If the line is longer, and we want to use a different color for 2nd person, use \n to break up the lines, and insert CFn for color:

0:07:37.42 0:07:38.42 D1JR    {Asuka} Whaddaya mean Joseph Chen\nhas my Wedding Peach LDs?
0:07:38.42 0:07:39.42 D1JLCF1 {Meimi} What?!

b.  2nd Person speak from background:

0:07:37.42 0:07:39.42 D1 {Asuka} Whaddaya mean?!
0:07:38.42 0:07:39.42 D1CF1 {Meimi} What?!\n

We use \n to bump up Meimi's line above Asuka's line, and have both lines go off-screen at the same time.  Even if Asuka's speech ends before 0:07:39.42, you should have it end with Meimi's line.  It refreshes the whole screen, and looks better.

c.  Top and bottom corners:

0:07:37.42 0:07:39.42 D1VTJL {Note1} Subtitled by\nFans for Fans
0:07:37.42 0:07:39.42 D1VBJR {Note2} Not for\nSale or Rent

VTJL will place your text at Top-Left, and VBJR will place your text at Bottom-Right.  Avoid using VPn to position your text as much as you can.  The JL and JR commands can be combined with VT, VM, and VB.  If you use  \n  and  ~  to format your text, you'd get less pixel collisions.

d.  Intro credits:

If you have a large block of text, like introduction credits to a show, I recommend using VMJLJBC.  The text will be centered on screen, with center block, left justified.

e.  Songs:

For op/ed songs, most anime shows have the Japanese text in white on-screen.  You must decide if you want to place the translated lyrics above the Japanese text, or cover it.

If you want to cover the Japanese text, it's better to use thicker outlines and drop-shadows (FO2FSSE2 for JACOsub 29) than an ugly black box.  Or, you can use a semi-transparent (shaded) box with the CSn command.  Alex suggests using CS8 or greater.

To place your lines above the Japanese text, you can usually get away with adding one \n to the end of each lines.  If it doesn't fit exactly, play with the VHn command -- remember to assign the song subtitles its own directive if you're going to do this.

f.  Songs with romanji (Japanese words spelled out in Roman alphabet by sound) + translation at same time:

If you want to have both kaorake romanji and the translation on-screen at the same time, I recommend 2 methods:

1.  Place one on top, and the other on the bottom.  Use separate line(s):
0:47:29.25 0:47:35.06 D8VT {Song2} KISS wo shite moraeru mae no
0:47:29.25 0:47:35.06 D8VB {Song2} If I'm asked now...
0:47:36.73 0:47:41.83 D8VT {Song2} namida no wake wo
0:47:36.73 0:47:41.83 D8VB {Song2} About the reason for the tears...

2.  Place both on bottom, use a single timed line for both.  Use \Cn to change color, and \n to divide the two, like this:
0:47:29.25 0:47:35.06 D8 {Song2} KISS wo shite moraeru mae no\n\C3If I'm asked now...
0:47:36.73 0:47:41.83 D8 {Song2} namida no wake wo\n\C3About the reason for the tears...
0:47:42.50 0:47:48.94 D8 {Song2} moshimo ima tazuneraretara\n\C3That flow before I can get you to kiss me...
0:47:50.07 0:47:54.91 D8 {Song2} dou sureba ii\n\C3Then, what can I do?

NOTE:  Remember to use smaller fonts!  I recommend FuturaB.font 20.


VIII.  Palette switching

a.  Using Superhires mode.

If you're using Super high-res mode (#H SUPERHIRES), you'd need to use Palette switching to get more colors.  Things to remember:

1.  Most JACOsub scripts that has palette switching use hexadecimal (0 to f) instead of decimal (0 to 15) for RGB values.  Don't ask me why, it's one of those secrets of the universe kind of thing.

2.  You can define and use up to 10 palettes, from 0-9, NOT 1-10.  The default palette is 0.  Each palette has 4 colors from 0 to 3.

3.  Despite having 4 colors to a palette, you really only get to modify 2 -- color 1 and 3.  Don't mess with color 0 and 2, leave them as is.

4.  Don't forget to use SuperHires fonts instead of the "regular" ones.


b.  A sample palette from Karinkuru Anime:

#P0 0 0 0 COLOR 0 BLACK
#P1 5 D E COLOR 1 BLUE
#P2 0 0 0 COLOR 2 BLACK
#P3 D D 8 COLOR 3 YELLOW

#P0 0 0 0 1 COLOR 0 BLACK
#P1 E E E 1 COLOR 1 WHITE PALETTE 1
#P2 0 0 0 1 COLOR 2 BLACK
#P3 D D 8 1 COLOR 3 YELLOW PALETTE 1

#P0 0 0 0 2 COLOR 0 BLACK
#P1 E 4 7 2 COLOR 1 RED PALETTE 2
#P2 0 0 0 2 COLOR 2 BLACK
#P3 E E E 2 COLOR 3 WHITE PALETTE 2

#P0 0 0 0 3 COLOR 0 BLACK
#P1 5 D E 3 COLOR 1 BLUE PALETTE 3
#P2 0 0 0 3 COLOR 2 BLACK
#P3 E E E 3 COLOR 3 WHITE PALETTE 3

The syntax for defining color palette is #Pn <R> <G> <B> <Palette>, like this:

#P1 14 14 1 1  # Yellow, Color 1, Palette 1
#P3  0 13 0 2  # Green, Color 2, Palette 2

c.  Revised palette settings.

No, you don't have to write out Color 0-3 for every palette like Karinkuru Anime did.  You can do it this way:

# Color Palette CP0
#P1 5 D E      # COLOR 1 BLUE
#P3 D D 8      # COLOR 3 YELLOW

# Color Palette CP1
#P1 E E E 1    # COLOR 1 WHITE
#P3 D D 8 1    # COLOR 3 YELLOW

# Color Palette CP 2
#P1 E 4 7 2    # COLOR 1 RED
#P3 E E E 2    # COLOR 3 WHITE

# Color Palette CP3
#P1 5 D E 3    # COLOR 1 BLUE
#P3 E E E 3    # COLOR 3 WHITE


VIV.  WinUAE.

WinUAE is an Amiga emulator for Windows 95/98/NT.  It will allow you to run JACOsub, and numerous Amiga programs on your IBM compatible machine.  Due to internal clock and timing differences between Amiga and IBM PC's, you cannot run JACOsub under WinUAE and get accurate timing for your scripts.

However, there are some benefits to running JACOsub on your IBM.  While most of us have a Pentium class or faster PC, our poor, neglected Amiga boxes are still running at 7.14 or 14 Mhz.  On a stock Amiga 2000, it takes 5 to 7 minuets to compile a 700 line JACOsub script.

On my Pentium II-350 machine running Windows NT 4.0, Sysinfo under WinUAE reports a performance of 5.4 MIPS, which is 1.1 times the performance of an Amiga 3000 with 68030-25 Mhz CPU.  When I test compile scripts for error, I like to use the Pentium II, because it's much faster than my Amiga 2000.

As of 08/99, the latest version of WinUAE is 0.8.8 R7.  You can download WinUAE at:
http://www.codepoet.com/UAE/
http://homepage.uibk.ac.at/homepage/c725/c72578/amiga/uae/

You'll need Amiga ROM binaries to run WinUAE.  The utility  transrom  under \WinUAE\Amiga Programs has been provided to create an ROM image file from your Amiga.  

Please do NOT ask me for Amiga ROM binaries.  You can buy a CD with all the Amiga ROM binaries from Clanto, with pre-configured, ready to run Amiga emulator:
http://www.amigaforever.com/

To customize your WinUAE desktop and make it look all pretty, go here:
http://www.emuunlim.com/aiab/

Note:  The " \ " key bug in WinUAE has been fixed with 0.8.6 R4.


X.  Amiga upgrades.

Are you still running that 7.14 mhz Amiga 2000?  For Belldandy's sake, please upgrade to something faster.

a.  Amiga 500 users:

Viper 520-33 CD Turbo:     http://www.powerc.com/
68EC020-33 CPU, 2 x 40pin IDE sockets for HD and CDROM, mounting space for standard 2.5" laptop HD's, 8 MB fast RAM, installed with kickstart 3.0 ROM (ask for 3.1!), compatible with DCE Mini Megi 2 MB Chip MEM adapter (www.softhut.com/apollo.html), advertised as "asynchronous design for full genlock compatibility".

b.  Amiga 600 users:

Apollo 630 Turbo:     http://www.paxtron.com/apollo.htm
68030-50 Mhz CPU, 1 standard 72pin SIMM socket for up to 32mb of RAM (get slim chip type).

My Amiga 600HD has an excellent 68030-40 accelerator w/8MB Fast RAM from Power Computing (www.powerc.com).  I'm not sure if they still sell this product, you may want to check with customer services.

The Amiga 600 or 600HD has a standard mini-IDE port, which can be used with almost any 2.5" laptop HD.  The small IDE cable also provides power to the HD, unlike their larger cousins (require separate power adapter).  A good place to shop for cheap 2.5" laptop HD is  www.pricewatch.com

Pre-3.5 Amiga operating systems cannot use more than 4 GB per HD, unless if you use 3rd party device drivers and hacks.  It's unlikely that you'd have more than 1 GB worth of JACOsub scripts anyway, so, don't bother buying >4 GB laptop HD.

c.  Amiga 1000/1500(UK) users:    Er, sorry, can't help you.

Amiga 1200 users:  You're in luck.  Amiga 1200 has the largest selection and lowest price on accelerators.  Buy one with extended IDE or SCSI controller, so you can attach a CDROM to your A1200.  Check with www.powerc.com, www.paxtron.com, and www.softhut.com.

d.  Amiga 2000/2500 users:

Apollo 2030/25, 2030/50:     www.paxtron.com/apollo.htm
Paxtron has the cheapest price I can find for Apollo accelerators.  They come with 2 x 72 pin SIMM sockets that take standard 72 pin SIMM modules, expandable up to 64 MBs RAM, and has built-in SCSI controller.  Paxtron also have good prices on new Amiga 2000 keyboards.  Be warned that anything you order from them may not arrive for some time.

Catweasel:     http://members.tripod.com/~apd2/catweasl.htm
The Budda & Catweasel combined controller add 3 IDE ports to your A2000/A2500, and allows you to use standard IBM floppy drives.  The bundle includes software support for ATAPI (IDE) CDROM and CD-R support.  Yes!  You can use those inexpensive IDE drives, and snob at those A1200/A4000 users!

Cyberstorm, Blizzard, Apollo 060, etc.:
68040, 68060, and PPC equipped accelerators for Amiga 2000/A2500 will cost you $500 to $1000.  For that much, you mind as well buy an Amiga 4000.  Don't bother unless if you can find an 040 accelerator used, and cheap.

Note on buying used A2000 accelerators:
Check the lower left corner of your A2000 motherboard for revision number, then ask the seller to check the accelerator's manual to see if there's compatibility issues.  If you're buying from ebay, don't place your bid until the last 30 seconds.

A stock A2000 can only access 8 MBs of expansion memory, plus 1 or 2 MBs of chip RAM.  If you buy a Commodore accelerator, such as the A2620 or A2630, additional 32bit "Fast RAM" should auto-config just fine.  If you buy a 3rd party accelerator, such as the 040-33 that I use, you may need 2.0 or newer ROM, and additional drivers & .lib files.  Otherwise, the accelerator will not function correctly.

Also, fast accelerators may not function with older hard disk or SCSI controllers, such as the A2090, A2091, and some GVP cards.  Fortunately, most 030 or better accelerators come with SCSI controller built on-board.  If not, buy a Catweasel/Budda IDE Zorro II card (see above).

e.  Amiga 3000/4000 users:  Your Amiga is already pretty fast.  My only suggestion is 3.1 ROM upgrade and a CDROM drive (if you don't already have one).  If you want to run Amiga OS 3.5, consider memory upgrades as well.

f.  Amiga OS 3.5 upgrade:

The newest Amiga OS version is 3.5.  Visit  http://www.amiga.com/amigaos35/index.html  for more info.

The minimum hardware requirements for OS 3.5 are:
   CD-ROM drive
   Hard Drive (with some free space!)
   68020 or higher CPU
   Amiga 3.1 ROM
   4 MB fast RAM

For better performance, Amiga Inc. recommends 68030 or better CPU, 8 MB Fast RAM, and graphics accelerator.  Since most of us use our Amiga for NTSC video subtitling, we really don't need a graphics accelerator or scan doubler.

To pre-order Amiga OS 3.5, visit:

www.antigravity.com   # For US customers.  Look in "Products" - "Specials".
www.powerc.com        # For UK customers.

Remember, if you don't have 3.1 ROM, you should order it with the 3.5 OS bundle.  If you don't know how to install a ROM chip, please ask SOMEONE ELSE to do it for you.  I've seen one too many newbies break pins on those things.

The ROM chip on A2000 is located near lower-right side of the motherboard, under where your floppy drive is.


For additional info on all Amiga related topics, please visit the Amiga Web directory at:
http://www.cucug.org/amiga.html




- finis.

